- 0 minutes to read

Release Notes

Mule ESB Logging Agent

Empower your integration landscape with end-to-end logging and business transaction monitoring from Mule ESB and MuleSoft—on-premise or in the cloud—using Nodinite. Gain actionable insights, ensure compliance, and enable self-service analytics for your business users.

graph LR subgraph "Mule based platform" roMule["Mule ESB / MuleSoft"] --> |log4j| roLA["Nodinite Log Agent"] end subgraph "Nodinite Environment" roLogAPI(fal:fa-cloud-arrow-down Log API) roLA --> |Logging| roLogAPI roLogAPI --> roDB(fal:fa-database Log Databases) end

Architecture: Mule ESB/MuleSoft logs are collected by the Nodinite Log Agent and delivered to the Nodinite Log API and Log Databases for advanced analytics.

  • Mule On-Premise – Use Log4J Log Appender files for robust, real-time logging.
  • Cloudhub / Anypoint – Leverage the built-in backend database and APIs for seamless cloud integration.

Nodinite empowers your business Users with secure, role-based Log Views for self-service access to integration logs and business events.

Important

Always set OriginalMessageTypeName for searchable business data - When logging from Mule ESB flows, the Message Types field determines which Search Field Expressions will extract business data (Order Numbers, Customer IDs, Invoice amounts, Transaction codes) from your logged messages. Without proper Message Types, features like Non-Events Monitoring, Business Process Modeling (BPM), and business-data searches in Log Views won't work. Set OriginalMessageTypeName or im_messageType in your Mule flows before deploying to production.

Features

Nodinite offers two powerful approaches to enable message logging from Mule ESB flows:

  1. Mule ESB - Custom Connector – Recommended! This approach eliminates the need for the Nodinite Mule ESB Logging Agent by using Asynchronous Logging and the Nodinite Pickup Log Events Service Logging Agent. Enjoy maximum performance and flexibility.
  2. Built-in Logging shape – Not recommended for most scenarios, but supported for compatibility.

The Nodinite Mule ESB Logging Agent processes output from the second option, capturing logs (log4j) with message payloads and promoted properties from your Mule ESB flows.

Supported Versions

Nodinite supports all editions of Mule ESB and MuleSoft, including standalone runtime and Enterprise, from version 3.6.x and onwards.

Why choose Nodinite for MuleSoft logging?

  • Gain full visibility into business transactions and technical events across your hybrid integration landscape
  • Empower business users with secure, self-service access to logs and analytics
  • Accelerate troubleshooting and compliance with advanced search and filtering
  • Integrate seamlessly with both on-premise and cloud MuleSoft deployments

Other

Explore the MuleSoft platform blog for additional insights and best practices.

Next Step

Install Mule Log Agent
Configuration of the Log Agent

Message Types - Critical for Search Field extraction from Mule ESB logged events
Search Field Expressions - Extract business data from Mule flow messages
Log Views - Search logged data by business identifiers
Non-Events Monitoring - Track message volumes and detect missing messages
Business Process Modeling (BPM) - End-to-end transaction tracking across Mule flows
Pickup Log Events Service Logging Agent
Add or manage Log Agents
Log Agents
Add or manage a Log View
Users